Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Made nested query resources replace the whole resource instead of merging new over old #21721

Conversation

modular-magician
Copy link
Collaborator

This allows fields to be unset using the same logic that any other field on any other resource would use.

Related to #14848

b/394945456#comment14

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

compute: fixed bug in `google_compute_router_nat` where `max_ports_per_vm` couldn't be unset once set.

Note: Technically this also allows nat_ip_allocate_option to be unset, but that field must be set for type = PUBLIC and can't be set for type = PRIVATE, and modifying type forces recreation, so there doesn't seem to be a case where it can actually be unset on update.

This doesn't impact google_compute_router_nat because the only optional field has send_empty_value set.

Derived from GoogleCloudPlatform/magic-modules#13234

…ging new over old (hashicorp#13234)

[upstream:2ba1acd7e865dce04fe3d0b4c1b136cbdb2f93e2]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician requested a review from a team as a code owner March 5, 2025 21:14
@modular-magician modular-magician merged commit dcae139 into hashicorp:main Mar 5, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant